Skip to main content

What’s New

Qrvey 8.7
Version 8.7 of the Qrvey platform is now available to customers! This version includes new features including area charts, the ability to pivot and export data, as well as numerous bug fixes and performance improvements.
Learn More
Qrvey 8.6
Version 8.6 of the Qrvey platform is now available to customers. This version includes several new feature enhancements and performance improvements.
Learn More
Required Update for 8.5.1
Attention 8.5.1 customers: for any 8.5.1 instance deployed prior to 08/05/2024, an update is required to ensure you are running the latest images.
Learn More
Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
Version: 8.2

Troubleshooting Deployment

Here are some common scenarios where a deployment could result in failure.

Deployment fails with a “Pipeline failed to reach a successful state. Current status is failed" message.​

This error usually happens when the deployment runs into an AWS Service quota limit. To find the underlying error:

  1. Open a new browser window or tab, navigate or log in to your AWS account.
  2. Navigate to AWS CodePipeline.
  3. Find the pipeline “Qrvey_*” with the failed state.
  4. Click on the pipeline name to open the details.
  5. Find a step with an error state.
    • If the failed step is of the “AWS Code Build” type, then you can click on details and follow the link to find the actual error message.
    • If the step is of the “AWS Cloudformation” type, you can find the error message by navigating to the AWS Cloudformation console and looking at the “Events” tab for the template that is in “FAILED” or “ROLLBACK_*” state. If this is a new deployment and the cloudformation stack is in ROLLBACK_COMPLETE status then you would need to delete the stack and then go back to CodePipeline to retry the step that failed.

Common service quota limits are:

  • S3 buckets: The deployment will create about 24 S3 buckets, whereas the default limit in AWS is 100.

Once you have resolved the issue, you can restart the deployment or upgrade by clicking on the Retry button in the Installation app. Alternatively, you can restart the pipeline directly from AWS Codepipeline to make sure it reaches the Successful state and then click on the Retry button in the installation app.

Emails are not received from the application.​

Qrvey platform uses AWS Simple Email Service (SES) to send all emails. These emails include signup verification, forgotten password, and Send Email action in the flows. By default, AWS SES is in a Sandbox mode where it only allows sending email to verified email addresses. To resolve this issue, you would need to open a support ticket with AWS from the same account used to install the platform and ask AWS to move the account out of the sandbox mode. It usually takes them around 24 hours to move an account out of the sandbox.

In the meantime, you can enable some emails by verifying them in SES. To verify an email:

  1. Navigate to AWS SES Console.
  2. Click on the Email Addresses menu option on the left.
  3. Click on the Verify a New Email Address button.